Bentley OpenUtilities CONNECT Edition Help

To Propagate Master Database Schema Changes to a Replica

This section covers the following scenarios of propagating Master Database Schema changes to a Replica.
  • Scenario 1: Propagating a schema change where user adds a new column or drops a column from a table.
  • Scenario 2: Propagating a drop table change.
  • Scenario 3: Propagating an add table change.
Parent topic: Database Replication Installation

Propagate Add or Drop Column change

  1. Refresh (Sync) clients to bring them up to date (data changes) if possible.
  2. Stop the Mobile Server.
  3. Run the alter table scripts on the master database.
  4. Alter the Publication Items.
    1. Update the appropriate text files (CHDATA_ALTER.TXT or UTILITY_ALTER.TXT) in ..\Program Files\Bentley\UtilitiesDesigner\, with list of tables altered.
    2. At the command prompt, run the ALTERPUBLICATIONITEMS.BAT utility, from ..\Program Files\Bentley\UtilitiesDesigner\, with the following parameters. Use parameters in the order specified and use a space to separate each value.
  5. Cmd:\> AlterPublicationItems <Server Name> <Master DB Instance> <Master User> <Master Password> <Repository DB Instance> <Repository User> <Repository Password> <Unique Name > <Workflow Manager Username>

    Where:

    • Host name of the Master Oracle Server database
    • Oracle SID of the Master database
    • Username for connecting to Master database
    • Password for the Master User
    • Oracle SID of the Repository database (Usually the same as Master database)
    • Username for Repository user (Usually MOBILEADMIN)
    • Password for the Repository User
    • A name for the Workflow Manager Replication Publication
      Note: This name must be only two characters.
    For Example: Cmd:\> AlterPublicationItems geobox elecxm chdata chadmin elecxm mobileadmin chadmin WM
  6. Restart the Mobile Server.
  7. Refresh (Sync) Clients to bring them up to date (propagate schema change)

Propagate Drop Table change

Because of the following Oracle Lite bug we have to execute a drop table script on every Oracle Lite client database to finally remove the table:

Note: Bug No. 4055479Product Version: Oracle 10g Lite

DROPPING A QUEUE BASED PUBLICATION ITEM DOES NOT DROP THE TABLE ON THE CLIENT

This is a known limitation of the product. The datas stay side client, the snapshot will remain on the device but will no longer be included in the synchronization process. The application should remove the snapshot once it is no longer needed.

  1. Refresh (Sync) clients to bring them up to date (data changes) if possible.
  2. Stop the Mobile Server.
  3. Drop the Publication Items.
    1. Update the appropriate text files (CHDATA_DROP.TXT or UTILITY_DROP.TXT) in ..\Program Files\Bentley\UtilitiesDesigner, with list of tables altered.
    2. At the command prompt, run the DROPPUBLICATIONITEMS.BAT utility, from ..\Program Files\Bentley\UtilitiesDesigner\, with the following parameters. Use parameters in the order specified and use a space to separate each value.
  4. Cmd:\> DropPublicationItems <Server Name> <Master DB Instance> <Master User> <Master Password> <Repository DB Instance> <Repository User> <Repository Password> <Unique Name > < Workflow Manager Username>

    Where:

    • Host name of the Master Oracle Server database
    • Oracle SID of the Master database
    • Username for connecting to Master database
    • Password for the Master User
    • Oracle SID of the Repository database (Usually the same as Master database)
    • Username for Repository user (Usually MOBILEADMIN)
    • Password for the Repository User
    • A name for the Workflow Manager Replication Publication
      Note: This name must be only two characters.
    For Example: Cmd:\> DropPublicationItems geobox elecxm chdata chadmin elecxm mobileadmin chadmin WM
  5. Restart the Mobile Server.
  6. Run the drop table scripts on the Oracle Lite Client databases.
  7. Refresh (Sync) Clients to bring them up to date (propagate schema change).

Propagate Add Table change

  1. Refresh (Sync) clients to bring them up to date (data changes) if possible.
  2. Stop the Mobile Server.
  3. Run the add table scripts on the master database.
  4. Add the Publication Items.
    1. Update the appropriate text files (CHDATA_ADD.TXT or UTILITY_ADD.TXT) in ..\Program Files\Bentley\UtilitiesDesigner, with list of tables altered.
    2. At the command prompt, run the ADDPUBLICATIONITEMS.BAT utility, from ..\Program Files\Bentley\UtilitiesDesigner\, with the following parameters. Use parameters in the order specified and use a space to separate each value.
  5. Cmd:\> AddPublicationItems <Server Name> <Master DB Instance> <Master User> <Master Password> <Repository DB Instance> <Repository User> <Repository Password> <Unique Name> < Workflow Manager Username>

    Where:

    • Host name of the Master Oracle Server database
    • Oracle SID of the Master database
    • Username for connecting to Master database
    • Password for the Master User
    • Oracle SID of the Repository database (Usually the same as Master database)
    • Username for Repository user (Usually MOBILEADMIN)
    • Password for the Repository User
    • A name for the Workflow Manager Replication Publication
      Note: This name must be only two characters.
    For Example: Cmd:\> AddPublicationItems geobox elecxm chdata chadmin elecxm mobileadmin chadmin WM
  6. Restart the Mobile Server.
  7. Run the drop table scripts on the Oracle Lite Client databases.
  8. Refresh (Sync) Clients to bring them up to date (propagate schema change).